src/sandboxes/__tests__/copyOpenClawToRepo.test.ts (1)

9-11: Remove the empty JSDoc block.

The comment block at Line 9–Line 11 is empty and adds noise in tests; please remove it unless you plan to document behavior there.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/sandboxes/__tests__/copyOpenClawToRepo.test.ts` around lines 9 - 11,
Remove the empty JSDoc block (the standalone "/** */" comment) present near the
top of the test file; simply delete that empty comment so the test file no
longer contains the unused JSDoc noise and ensure there are no other empty JSDoc
blocks left in the same file.

src/content/transcribeSong.ts (2)

71-75: Incomplete JSDoc parameters add noise without value.

The @param tags list only parameter names without descriptions. Either provide meaningful descriptions or remove these empty annotations—the function signature already conveys the parameter names.

📝 Suggested fix: Complete or remove JSDoc params

Option 1 - Complete the documentation:

 /**
  * Gets the lyrics for a specific time range within a song.
- *
- * `@param` lyrics
- * `@param` startSeconds
- * `@param` endSeconds
+ * `@param` lyrics - The full song lyrics with timestamped segments
+ * `@param` startSeconds - Start of the time range in seconds
+ * `@param` endSeconds - End of the time range in seconds
+ * `@returns` Object containing concatenated lyrics text and matching segments
  */

Option 2 - Remove empty params:

 /**
  * Gets the lyrics for a specific time range within a song.
- *
- * `@param` lyrics
- * `@param` startSeconds
- * `@param` endSeconds
  */

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/transcribeSong.ts` around lines 71 - 75, The JSDoc above the
transcribeSong function contains `@param` entries with only parameter names and no
descriptions, which is noisy; either remove those empty `@param` tags or replace
them with concise descriptions for each parameter (e.g., explain lyrics,
startSeconds, endSeconds and their types/units) in the JSDoc for function
transcribeSong so the docblock is meaningful and matches the function signature.

---

76-84: Multiple exports violate Single Responsibility Principle.

This file exports both transcribeSong and getLyricsForTimeRange. Consider extracting getLyricsForTimeRange to a separate utility file (e.g., src/content/lyricsUtils.ts) to comply with the one-exported-function-per-file guideline.

As per coding guidelines: "Implement SRP (Single Responsibility Principle): have one exported function per file".

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/transcribeSong.ts` around lines 76 - 84, The file currently
exports both transcribeSong and getLyricsForTimeRange; extract
getLyricsForTimeRange into its own module by creating a new file that exports
getLyricsForTimeRange (keeping its signature and returning { clipLyrics,
segments }), import any needed types (SongLyrics, LyricSegment) into that new
module, update the original file to remove the getLyricsForTimeRange export and
replace its internal references with an import of getLyricsForTimeRange from the
new module, and run/adjust any unit tests or callers to import the function from
the new module so each file only exports one main function.

src/pulse/executePulseInSandbox.ts (1)

22-27: Remove redundant auto-generated JSDoc params.

Lines 22-23 already document params.accountId and params.prompt. The root0 parameters (lines 24-26) appear to be auto-generated artifacts that duplicate this documentation and add confusion. Remove the redundant entries.

Suggested fix

 /**
  * Executes a pulse in a sandbox by calling POST /api/sandboxes with a prompt.
  * The API creates/resumes a sandbox and runs the prompt via OpenClaw.
  *
  * `@param` params.accountId - The account ID to execute the pulse for
  * `@param` params.prompt - The pulse prompt to execute
- * `@param` root0
- * `@param` root0.accountId
- * `@param` root0.prompt
  * `@returns` The sandbox ID and run ID on success, undefined on error
  */

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/pulse/executePulseInSandbox.ts` around lines 22 - 27, The JSDoc contains
redundant autogenerated param entries (root0, root0.accountId, root0.prompt)
that duplicate params.accountId and params.prompt; edit the JSDoc for
executePulseInSandbox to remove the redundant root0* param lines so only the
meaningful params (params.accountId and params.prompt) remain and the return
description stays intact.

src/content/upscaleImage.ts (1)

40-43: Complete or remove incomplete JSDoc block.

The JSDoc has an empty description and @param data without any explanation. Either provide meaningful documentation or remove the comment.

Suggested fix

-/**
- *
- * `@param` data
- */
+/** Extracts the output URL from a fal.ai response payload. */
 function extractFalUrl(data: Record<string, unknown>): string | undefined {

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/upscaleImage.ts` around lines 40 - 43, The JSDoc above the
upscaleImage function is incomplete (empty description and a bare "@param
data"); either remove the entire JSDoc block or replace it with a concise
docstring that describes what upscaleImage does, documents the "data" parameter
(type and expected shape/properties) and the return value/promise (e.g.,
processed image buffer or response). Update the JSDoc near the upscaleImage
function to include a short one-line description, "@param data {Type} -
description" and an "@returns {Type} - description" or simply delete the /** ...
*/ block if you prefer no comment.

src/sandboxes/getSandboxEnv.ts (1)

4-6: Complete the JSDoc @param description.

The @param accountId tag is missing a description. Add a brief explanation of what the parameter represents.

Suggested fix

 /**
  * Builds the environment variables to inject into sandbox commands.
  * Shared by runSandboxCommandTask and codingAgentTask.
  *
- * `@param` accountId
+ * `@param` accountId - The account identifier to include in the environment
  */

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/sandboxes/getSandboxEnv.ts` around lines 4 - 6, Add a brief description
for the JSDoc `@param` tag for accountId in the getSandboxEnv function: explain
that accountId is the unique identifier (string or number) for the user/account
whose sandbox environment variables should be retrieved or used to load the
sandbox configuration. Update the JSDoc comment above getSandboxEnv to include
this description.

src/sandboxes/__tests__/snapshotAndPersist.test.ts (1)

15-17: Remove empty JSDoc comment block.

This JSDoc block is empty and provides no documentation value. Either add a meaningful description for createMockSandbox or remove the comment entirely.

Suggested fix

-/**
- *
- */
 function createMockSandbox() {

Or add a meaningful description:

-/**
- *
- */
+/** Creates a mock Sandbox with a stubbed snapshot method for testing. */
 function createMockSandbox() {

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/sandboxes/__tests__/snapshotAndPersist.test.ts` around lines 15 - 17,
Remove the empty JSDoc block above createMockSandbox: either delete the blank
/** */ entirely or replace it with a concise meaningful description for the
createMockSandbox helper (one-line summary of purpose and behavior), ensuring
the comment directly precedes the createMockSandbox declaration.

src/content/upscaleVideo.ts (2)

46-49: Complete or remove incomplete JSDoc block.

Same issue as in upscaleImage.ts - the JSDoc has an empty description and @param data without explanation.

Suggested fix

-/**
- *
- * `@param` data
- */
+/** Extracts the output URL from a fal.ai response payload. */
 function extractFalUrl(data: Record<string, unknown>): string | undefined {

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/upscaleVideo.ts` around lines 46 - 49, The JSDoc above the
upscaleVideo function is incomplete — either fill in a meaningful description
and document the `data` parameter (its expected type and any properties used by
upscaleVideo, e.g., input path, output path, scaleFactor, options) or remove the
empty JSDoc block entirely; update the comment immediately above the
upscaleVideo function to include a one-line summary and a proper `@param {Type}
data` description that matches the function's actual parameter shape.

---

50-64: Extract extractFalUrl to a shared utility module.

This helper function is duplicated identically across at least five content files (upscaleVideo.ts, upscaleImage.ts, generateContentImage.ts, generateContentVideo.ts, and generateAudioVideo.ts). Extract it to a dedicated utils module (e.g., src/content/utils/falUrlExtractor.ts) and import it in all files to follow the DRY principle.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/upscaleVideo.ts` around lines 50 - 64, Extract the duplicated
function extractFalUrl into a single exported helper module (create and export a
function named extractFalUrl in a new utils module), update each file that
currently defines it (upscaleVideo.ts, upscaleImage.ts, generateContentImage.ts,
generateContentVideo.ts, generateAudioVideo.ts) to remove the local
implementation and import { extractFalUrl } from the new module, and ensure the
imported function signature and behavior remain unchanged so calls to
extractFalUrl(data: Record<string, unknown>) continue to work as before.

src/sandboxes/__tests__/syncOrgRepos.test.ts (1)

10-12: Remove empty JSDoc comment block.

This empty JSDoc block adds no documentation value. Either add a meaningful description for createMockSandbox or remove the comment entirely.

📝 Suggested options

Option 1: Remove empty comment

-/**
- *
- */
 function createMockSandbox() {

Option 2: Add meaningful description

-/**
- *
- */
+/** Creates a mock sandbox with a stubbed runCommand method for testing. */
 function createMockSandbox() {

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/sandboxes/__tests__/syncOrgRepos.test.ts` around lines 10 - 12, Remove
the empty JSDoc block at the top of the test file (the blank /** */) — either
delete it entirely or replace it with a short meaningful description for the
createMockSandbox helper (referencing createMockSandbox) so the file no longer
contains a useless empty JSDoc comment; update the comment to describe the
helper’s purpose if you choose to keep it.

src/content/fetchArtistContext.ts (1)

4-7: Consider adding parameter descriptions to JSDoc.

The parameter annotations lack descriptions. Adding brief descriptions would improve documentation clarity.

📝 Suggested improvement

 *
-* `@param` githubRepo
-* `@param` artistSlug
-* `@param` fetchFile
+* `@param` githubRepo - GitHub repository URL
+* `@param` artistSlug - Artist directory identifier
+* `@param` fetchFile - Function to fetch file content from the repository
 */

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/fetchArtistContext.ts` around lines 4 - 7, Update the JSDoc for
the fetchArtistContext function by adding brief descriptions for each `@param`:
describe githubRepo (e.g., the GitHub repository identifier or client used),
artistSlug (the artist's unique slug used to locate their content), and
fetchFile (the helper/function used to fetch files or a flag indicating file
retrieval behavior), and also ensure the return/throws tags (if present) are
meaningful; modify the JSDoc block immediately above fetchArtistContext to
include these parameter descriptions.

src/content/listArtistSongs.ts (2)

7-8: JSDoc parameter annotations are incomplete.

The JSDoc @param tags lack descriptions. Either add meaningful descriptions or remove the empty parameter annotations to avoid documentation noise.

 * `@param` githubRepoUrl
 * `@param` artistSlug

Could be:

-* `@param` githubRepoUrl
-* `@param` artistSlug
+* `@param` githubRepoUrl - The GitHub repository URL to search
+* `@param` artistSlug - The artist's slug identifier for folder lookup

Also applies to: 45-47

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/listArtistSongs.ts` around lines 7 - 8, The JSDoc for the
function listArtistSongs (and other JSDoc blocks around lines 45-47) contains
`@param` tags with empty descriptions (e.g., `@param` githubRepoUrl, `@param`
artistSlug); update these JSDoc comments by adding concise descriptions for each
parameter (what they represent and expected type/format) or remove the empty
`@param` lines entirely so the documentation is not noisy—look for the JSDoc block
above the listArtistSongs function and any subsequent blocks at the indicated
region and either fill in meaningful descriptions for githubRepoUrl and
artistSlug (and any other empty params) or delete those `@param` annotations.

---

11-14: Multiple exported functions violate SRP guideline.

This file exports both listArtistSongs and parseSongPath. As per coding guidelines, files should have "one exported function per file."

Consider extracting parseSongPath to a separate file (e.g., src/content/parseSongPath.ts) since it's used by consumers to decode the encoded paths.

Also applies to: 48-57

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/listArtistSongs.ts` around lines 11 - 14, This file currently
exports both listArtistSongs and parseSongPath which breaks the
one-export-per-file rule; extract parseSongPath into its own module (e.g.,
create src/content/parseSongPath.ts) and export it from there, remove its export
from src/content/listArtistSongs.ts so only listArtistSongs remains exported,
and update any call sites/imports to import parseSongPath from the new module;
ensure function signature and runtime behavior of parseSongPath remain unchanged
and run tests to verify no import paths are broken.

src/sandboxes/__tests__/setupOpenClaw.test.ts (1)

13-15: Remove empty JSDoc comment.

The empty JSDoc block adds no value. Either remove it or add a meaningful description for createMockSandbox.

Suggested fix

-/**
- *
- */
 function createMockSandbox() {

Or add a proper description:

-/**
- *
- */
+/** Creates a mock Sandbox with stubbed runCommand method. */
 function createMockSandbox() {

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/sandboxes/__tests__/setupOpenClaw.test.ts` around lines 13 - 15, Remove
the empty JSDoc block above createMockSandbox in the test file; either delete
the blank /** */ entirely or replace it with a concise JSDoc describing the
createMockSandbox helper (e.g., its purpose and return value) so the comment is
meaningful and not an empty block.

src/recoup/scrapeSocial.ts (1)

17-19: Incomplete JSDoc @param tag.

The @param socialId is missing a description. Either complete it or remove the tag to avoid inconsistency with the rest of the documentation.

Suggested fix

 * Returns Apify run metadata that can be used to poll for status and retrieve results.
 *
- * `@param` socialId
+ * `@param` socialId - The social profile ID to scrape
 */

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/recoup/scrapeSocial.ts` around lines 17 - 19, The JSDoc for the function
handling social scraping contains an incomplete `@param socialId` tag; update
the JSDoc for the function (e.g., the scrapeSocial or equivalent function that
takes socialId) to either remove the orphan `@param` or add a concise
description like "socialId - the ID or handle of the social account to scrape"
so the param documentation is consistent and informative; locate the JSDoc block
above the function that references socialId and edit the `@param` line
accordingly.

src/github/getExistingGithubRepo.ts (1)

40-40: Consider using Zod for response validation.

The response is cast with a type assertion rather than validated. If the GitHub API response shape changes or returns an error object, this could lead to runtime issues when accessing html_url.

Suggested fix using Zod

+import { z } from "zod";
+
+const repoResponseSchema = z.object({
+  html_url: z.string(),
+});
+
 // In the function:
-    const data = (await response.json()) as { html_url: string };
+    const json = await response.json();
+    const result = repoResponseSchema.safeParse(json);
+
+    if (!result.success) {
+      logger.error("Invalid response from GitHub API", {
+        repoName,
+        errors: result.error.issues,
+      });
+      return undefined;
+    }
+
+    const data = result.data;

As per coding guidelines: "Use Zod for schema validation" applies to src/**/*.{ts,tsx} files.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/github/getExistingGithubRepo.ts` at line 40, The code casts the GitHub
response with a type assertion (const data = (await response.json()) as {
html_url: string }) which risks runtime errors; replace this with Zod
validation: import z from "zod", define a schema like repoSchema = z.object({
html_url: z.string().url() }), parse the JSON via repoSchema.parse(await
response.json()) or use safeParse and handle failures, then use the parsed
object's html_url; update any error handling in getExistingGithubRepo to
log/throw on validation failure instead of assuming the shape.

src/sandboxes/__tests__/addOrgSubmodules.test.ts (1)

13-15: Remove empty JSDoc block.

The JSDoc comment on the createMockSandbox helper is completely empty and adds no documentation value.

🧹 Suggested fix

-/**
- *
- */
 function createMockSandbox() {

Or add a meaningful description:

-/**
- *
- */
+/** Creates a mock sandbox with a stubbed runCommand method. */
 function createMockSandbox() {

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/sandboxes/__tests__/addOrgSubmodules.test.ts` around lines 13 - 15,
Remove the empty JSDoc block above the createMockSandbox helper in the test
file: delete the /** */ block entirely (or replace it with a concise meaningful
description of what createMockSandbox does), ensuring the createMockSandbox
declaration is left directly preceded by either no comment or a short
descriptive JSDoc comment.

src/content/fetchAudienceContext.ts (1)

4-7: Consider adding descriptions to JSDoc @param annotations.

The added @param annotations are empty and don't provide additional documentation value. Either add meaningful descriptions or remove them to avoid documentation noise.

📝 Suggested improvement

 /**
  * Fetches audience context (audience.md) from GitHub.
  * Returns placeholder if not found.
- *
- * `@param` githubRepo
- * `@param` artistSlug
- * `@param` fetchFile
+ * `@param` githubRepo - The GitHub repository URL
+ * `@param` artistSlug - The artist identifier/slug
+ * `@param` fetchFile - Function to fetch file content from repo
  */

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/fetchAudienceContext.ts` around lines 4 - 7, The JSDoc for
fetchAudienceContext currently lists `@param` githubRepo, `@param` artistSlug, and
`@param` fetchFile with no descriptions; update the JSDoc above the
fetchAudienceContext function in src/content/fetchAudienceContext.ts to either
remove those empty `@param` tags or replace them with short, meaningful
descriptions explaining each parameter's purpose (e.g., what type/value
githubRepo expects, what artistSlug represents, and what fetchFile does), and
add a brief `@returns` description if applicable.

src/content/fetchGithubFile.ts (1)

96-99: Empty JSDoc block adds no value.

The JSDoc for parseRepoUrl contains only an empty description and a parameter name without explanation. Either add meaningful documentation or remove the block entirely.

📝 Suggested improvement

-/**
- *
- * `@param` githubRepoUrl
- */
+/** Extracts owner and repo name from a GitHub URL. */
 function parseRepoUrl(githubRepoUrl: string): { owner: string; repo: string } {

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/fetchGithubFile.ts` around lines 96 - 99, The JSDoc above
parseRepoUrl is empty and adds no value; remove the empty block or replace it
with a concise description and parameter explanation (e.g., describe what
parseRepoUrl does, the expected format of githubRepoUrl, and the return value).
Update the JSDoc for parseRepoUrl to include meaningful text for the
githubRepoUrl param and the function's return type/behavior, or delete the /**
... */ block entirely if you prefer no doc comment.

src/recoup/fetchTask.ts (1)

30-32: Add a short description to @param externalId.

The tag is present but currently not descriptive.

📝 Suggested doc tweak

- * `@param` externalId
+ * `@param` externalId - External task ID used to fetch the task from the Recoup Tasks API.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/recoup/fetchTask.ts` around lines 30 - 32, Add a one-line description for
the JSDoc `@param` externalId in the fetchTask function: describe that externalId
is the external system identifier (e.g., third-party or upstream task ID) used
to locate or fetch the task, so update the comment above fetchTask to read a
short phrase like "externalId - external system/task identifier used to fetch
the task."

src/sandboxes/__tests__/runOpenClawAgent.test.ts (1)

15-21: Trim or complete the new JSDoc blocks.

These docblocks are currently empty/low-signal. Either add meaningful descriptions or remove them to keep test helpers concise.

✂️ Suggested cleanup

-/**
- *
- * `@param` finished
- * `@param` finished.exitCode
- * `@param` finished.stdout
- * `@param` finished.stderr
- */
 function mockDetachedCommand(finished: {
   exitCode: number;
   stdout: () => Promise<string>;
   stderr: () => Promise<string>;
 }) {
   return { wait: vi.fn().mockResolvedValue(finished) };
 }
 
-/**
- *
- */
 function createMockSandbox() {
   const runCommand = vi.fn();
   return { runCommand } as any;
 }

Also applies to: 30-32

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/sandboxes/__tests__/runOpenClawAgent.test.ts` around lines 15 - 21, The
JSDoc block for the test helper parameter "finished" is empty/low-signal—either
remove the docblock entirely or replace it with concise descriptions for the
parameter and its properties (finished.exitCode, finished.stdout,
finished.stderr); update the JSDoc above the helper function used in
runOpenClawAgent.test.ts (the function that accepts the "finished" param) to
include a one-line summary and short `@param` lines describing each property, or
delete the entire block to keep the test helper concise.

src/content/generateAudioVideo.ts (1)

88-94: JSDoc @param tags lack descriptions.

The @param annotations are present but empty, which doesn't add value. Either add meaningful descriptions or remove the empty tags.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/generateAudioVideo.ts` around lines 88 - 94, Update the JSDoc for
the clip function in src/content/generateAudioVideo.ts by either removing the
empty `@param` tags or, preferably, adding concise descriptions for each parameter
used by the function (songBuffer, startSeconds, durationSeconds) and any return
value; for example document that songBuffer is the MP3 file buffer, startSeconds
is the clip start time in seconds, and durationSeconds is the clip length in
seconds so the JSDoc on the function (the block above the clip/clipSong or
generateAudioVideo function) provides meaningful parameter documentation.

src/recoup/getArtistSocials.ts (1)

34-37: Empty JSDoc @param tag.

Same pattern as other files — the @param annotation lacks a description.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/recoup/getArtistSocials.ts` around lines 34 - 37, The JSDoc for
getArtistSocials has an empty `@param` tag; update the comment above the
getArtistSocials function to provide a clear description for the artistAccountId
parameter (e.g., "artistAccountId - the unique identifier or account ID of the
artist whose social links are being retrieved") so the `@param` is not blank and
matches the style used in other files.

src/content/loadTemplate.ts (1)

26-27: Empty JSDoc @param tags don't add documentation value.

Multiple functions have @param paramName annotations without descriptions. Either add meaningful descriptions or remove the empty tags to avoid clutter.

Also applies to: 81-82, 93-95, 128-129, 145-149

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/loadTemplate.ts` around lines 26 - 27, Remove or fill empty JSDoc
`@param` tags in this file: update the JSDoc blocks for loadTemplate and the other
documented functions (e.g., getTemplate, compileTemplate, renderTemplate) so
each `@param` either has a concise description or is removed entirely; ensure the
remaining JSDoc tags accurately describe parameter names shown in the
corresponding function signatures (match symbol names loadTemplate, getTemplate,
compileTemplate, renderTemplate) and keep the comments minimal and relevant.

src/content/testPipeline.ts (1)

50-58: Empty JSDoc blocks throughout the file add no documentation value.

Multiple functions have JSDoc blocks with no content (e.g., loadState, saveState, setupFal, testImage, etc.). These empty comment blocks clutter the code without providing documentation. Either add meaningful descriptions or remove them.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/testPipeline.ts` around lines 50 - 58, Remove or populate the
empty JSDoc blocks that provide no value: locate the empty /** */ comments above
functions like loadState, saveState, setupFal, testImage, etc., and either
delete those empty JSDoc blocks or replace them with brief meaningful
descriptions and param/return tags where appropriate (e.g., describe what
loadState returns and what saveState persists). Ensure any added JSDoc
accurately references the function signature (parameters and return types) and
keep comments concise.

src/socials/filterScrapableSocials.ts (1)

15-17: Empty JSDoc parameter descriptions provide no value.

The @param annotations lack descriptions. Either add meaningful documentation or remove the empty annotations to reduce noise.

 * Filters and collects all scrapable socials from the artist socials map.
 * Returns an array of scrapable socials with their associated artist IDs.
- *
- * `@param` artistIds
- * `@param` artistSocialsMap
 */

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/socials/filterScrapableSocials.ts` around lines 15 - 17, The JSDoc for
filterScrapableSocials contains empty `@param` tags for artistIds and
artistSocialsMap which are noisy; update the JSDoc by either removing those
empty `@param` annotations or replacing them with brief, meaningful descriptions
(e.g., describe that artistIds is an array of artist identifiers and
artistSocialsMap is a map/object of social links keyed by artist ID) so the
function header documents its inputs clearly.

src/socials/scrapeAndPollSocials.ts (1)

12-14: Empty JSDoc parameter descriptions.

Same issue as other files—@param tags without descriptions add clutter without value.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/socials/scrapeAndPollSocials.ts` around lines 12 - 14, The JSDoc for the
scrapeAndPollSocials function contains empty `@param` tags that add noise; either
remove the empty `@param` entries or replace them with concise descriptions for
the parameters (e.g., describe "socials" and "batchSize") in the JSDoc block for
the scrapeAndPollSocials function so the comment is meaningful and consistent
with other files.